Announcements
- Khoros is now part of the IgniteTech family. Learn More.
Featured Content
Monthly digest to provide all users a reliable snapshot of product updates, as well as any other resources that can provide inspiration or guidance.
Community Experience Surveys (formerly Value Analytics) enable you to gather responses directly from members through short in-product prompts. You control who sees the survey, when it appears, how of...
We are excited to announce live training on Launching Best Practices in Khoros Communities are coming in June 2025!
Wednesday, June 4, 2025 Early Session: 7 am CDT / 12 pm UTC Late Session: 12 p...
Seamless customer journeys start with community. Join this virtual masterclass to learn how.
Thursday, May 08, 2025 | 9am PT | 11am CT | 12pm ET
Click the link above to secure your spo...
Recent Content
Pull different Aurora community content into an RSS feed using URLs
You can pull different community content from different levels in the community in an RSS feed using URLs. To pull the most recent RSS results for the entire community, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Community For example, for Atlas, you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Community To pull content over the RSS for a category, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Category?category.id=[CategoryID] For example, if Atlas had a category with the ID of "Social," you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Category?category.id=Social Note: Category IDs are case sensitive. To pull content over the RSS for a KB, use: https://yourdomain.com/t5/s/[CommunityID]/rss/Community?interaction.style=tkb For example, for Atlas you'd use: https://community.khoros.com/t5/s/lithosphere/rss/Community?interaction.style=tkbCannot successfully archive message via API v2
Has anyone been able to successfully archive a message using the Community API v2 POST call documented in the Developer Docs? I've tried several ways and can't seem to get it to work. For example: Using the restadmin directive <#assign response = restadmin("2.0", "/archives/archive", "POST", {"messageId": "32815"}) /> Status: ${response.status}<br /> Message: ${response.message}<br /> Data Keys:<br /> <#list response.data?keys as dataKey> - ${dataKey}<br /> </#list> Using the restBuilder directive <#assign archivePostCall = restBuilder() .method("POST") .path("/archives/archive") .body({"messageId": "32815"}) .admin(true) /> <#assign response = archivePostCall.call() /> Status: ${response.status}<br /> Message: ${response.message}<br /> Data Keys:<br /> <#list response.data?keys as dataKey> - ${dataKey}<br /> </#list> Both attempts above returned the following response: Status: error Message: Error generating JSON response. Data Keys: - getClass - validTemplateModelObject - toSerializedString - isValidTemplateModelObject - hashCode - equals - get - toString - class I tried performing the same operation via Python (as shown below) but the response is either a 400 or 500 error depending on whether or not I explicitly define the "content-type" header as "application/json" in my request. Attempt #1: Python 3.7.6 (tags/v3.7.6:43364a7ae0, Dec 19 2019, 00:42:30) [MSC v.1916 64 bit (AMD64)] on win32 >>> from khoros import Khoros >>> khoros = Khoros() >>> response = khoros.post('/api/2.0/archives/archive', {'messageId': '32815'}, return_json=False) >>> response <Response [400]> >>> response.text '{"status":"error","message":"A possible invalid request has been made. Make sure you are following the API spec and have used the correct URL, are included all required parameters and if a request payload is required you have included one.","data":{"type":"error_data","code":309,"developer_message":"","more_info":""},"metadata":{}}' >>> response.request.url 'https://REDACTED.com/api/2.0/archives/archive' >>> response.request.body '{"messageId": "32815"}' >>> response.request.headers {'User-Agent': 'python-requests/2.23.0', 'Accept-Encoding': 'gzip, deflate', 'Accept': '*/*', 'Connection': 'keep-alive', 'li-api-session-key': 'REDACTED', 'Content-Length': '22'} Attempt #2: >>> response = khoros.post('/api/2.0/archives/archive', {'messageId': '32815'}, headers={'content-type': 'application/json'}, return_json=False) >>> response <Response [500]> >>> response.text '{"status":"error","message":"An unexpected error occurred.","data":{"type":"error_data","code":301,"developer_message":"Can not deserialize instance of java.util.ArrayList out of START_OBJECT token\\n at [Source: org.apache.catalina.connector.CoyoteInputStream@34f637da; line: 1, column: 1]","more_info":""},"metadata":{}}' >>> response.request.headers {'User-Agent': 'python-requests/2.23.0', 'Accept-Encoding': 'gzip, deflate', 'Accept': '*/*', 'Connection': 'keep-alive', 'li-api-session-key': 'REDACTED', 'content-type': 'application/json', 'Content-Length': '22'} I was hoping I could do a network trace of the archival process in the web UI to see what the syntax should be, but it looks like a different UI-specific endpoint and form is used to perform the operation so I couldn't learn anything from it. Any help with this would be greatly appreciated. Thanks!
Featuring a topic in Khoros Classic
Hi all, I'm looking for a way to be able to feature a give topic via the REST API v2. I tried doing this in a test endpoint, <#assign feature_call = restBuilder() .method("PUT") .path("/messages/11577") .body({ "data": { "type": "message", "conversation": { "featured": true } } }) .admin(true) /> but it fails with the following error: { "status":"error", "message":"The following parameters, or the value passed in for them, are not valid: [featured].", "data":{ "type":"error_data", "code":404, "developer_message":"The parameter featured is not allowed in an 'update' call.", "more_info":"" }, "metadata":{} } I couldn't find anything in the REST API v1 either. Is there no way to actually feature a message via the API?Khoros Communities: Aurora 25.04 Release Notes
10 MIN READ This release brings new tools to help you manage and protect your community. You can now move and merge content across types, mute inbox conversations, and view history for all content types. We've enhanced security checks for images and private messages, and admins can now prompt members for feedback and export their responses. Additionally, there are enhancements to GraphQL. Several bugs are also fixed.Getting a 414 error code when updating messages via API
We have a third party tool where we can update messages in TKBs. I'm using the session key for authentication using a non-SSO user with their username and password to get and refresh the session key. The user has Admin permissions across the entire community (for testing this), their email is verified, I've checked to make sure their account is correctly set up and working and that their permissions are correct. However, when I run the call for certain TKBs, I get this error: {"status":"error","message":"Permission Denied","data":{"type":"error_data","code":414,"developer_message":"","more_info":""},"metadata":{}} But when I run it for other TKBs, I don't get the error. I've looked at both TKBs and I'm scratching my head. Permissions are the same, settings are the same, essentially everything is the same besides which category they're in, but I've checked permissions in all categories/sub-categories and there are no differences. Any idea why this would happen or why I'm getting Permission Denied for a user with Admin permissions in some TKBs but not others?Aurora SEO: Regulate content crawling by search engines using robots.txt
When you publish content in the community, search engines (web robots or web crawlers) crawl these newly published pages to discover and gather information from them. After crawling the content, the search engines index these pages to provide relevant search results based on the search queries. It is important to instruct the web crawlers to crawl only the relevant pages and ignore the pages that don't require crawling activity. Using Robots Exclusion Protocol (a file called robots.txt), you can indicate the resources that need to be included or excluded from the crawling activity. When a new community is created, the Khoros platform configures the robots.txt file with the default rules for the community. The default rules include instructions, which are generic for all the communities. Admins and members with permissions can view the Default Rules in Robots.txt Editor (from Settings > System > SEO area). In the editor, you can also add Custom Rules that are appended after the default rules. Note: You cannot edit the default rules. How does Robots.txt work? You can find the robots.txt file in the root directory of your community by appending “robots.txt” at the end of the URL (https://site.com/robots.txt). The file includes the list of user agents (web robots), community URLs, and sitemaps with instructions indicating whether the user agents are allowed or disallowed to crawl the specified URLs. When the user-agents or web crawlers enter your website, they first read the robots.txt file and proceed further with the crawling activity based on the instructions added in the file. The user-agents gather information only from the community pages that are allowed and are blocked from the pages that are disallowed. Robots.txt syntax The robots.txt includes these keywords that are widely used to specify the instructions: User-agent: The name of the web crawler for which you are providing the instructions. Example: User-agent: testbot To provide instructions to all the user agents at a time, enter * (wildcard character). Example: User-agent: * Disallow: Command to indicate the user-agents not to crawl the specified URL. Note that the URL must begin with ‘/’ (forward slash character). Example: User-agent: testbot Disallow: /www.test1.com Allow: Command to indicate the user-agents that they can crawl the specified URL. Note that the URL must begin with ‘/’ (forward slash character). Example: User-agent: testbot Allow: /www.test2.com Sitemap: Indicates the location of any XML sitemaps associated with the URL. The Khoros platform automatically generates sitemaps for each community when it is created and adds them to the robots.txt file. Example: User-agent: testbot Sitemap: https://www.test.com/sitemap.xml The following is the sample format to allow or disallow a user-agent "testbot” to crawl the community pages: User-agent: testbot Disallow: /www.test.com Allow: /www.test1.com Sitemap: https://www.test.com/sitemap.xml Using the Robots.txt Editor The Robots.txt Editor enables you to add, edit, and remove custom rules to robots.txt. You can look for more information provided by Google and other crawlers handling rules in robots.txt. Let’s take an example where you want to add a custom rule to disallow a user-agent “testbot” from crawling a member profile page of the community. To add a custom rule: Sign in to the community as an Admin. Go to Settings > System > SEO. In the Robots.txt Editor, you can view the Default Rules and Custom Rules sections. In the Custom Rules section, click Edit. In the Edit window, enter the instructions and click Save. The rule appears in the Custom Rules area of the tab. You can edit or remove the existing Custom Rules by clicking the Edit option. The new custom rules get appended to the robots.txt file located in the root directory: After you edit the custom rules, you can validate the robots.txt via the Lighthouse tool. Learn more about robots.txt validation using lighthouse. Note: The Audit log records the member actions made in the robots.txt file.
Featured Places
Education & Training
Self-service first product education experiences to maximize Khoros product adoptionHelp & Support
Find solutions and support for Khoros products
